Configurable transaction management controller and method thereof

ABSTRACT

Technologies for managing payment authorization request messaging for payment transactions include a transaction management controller for receiving a transaction amount for a payment transaction from a business management engine and payment card data for the payment transaction from a point of interaction device. The transaction management controller inserts the transaction amount and the payment card data into a payment authorization request message, which is transmitted to a payment network. A payment authorization response message is received from the payment network and transmitted by the transaction management controller the business management engine. Other embodiments are described and claimed.

TECHNICAL FIELD

Embodiments of the technologies described herein relate, in general, tothe field of payment transactions. More particularly, the technologiesdescribed herein relate to the field of managing payment authorizationrequest messaging for payment transactions.

BACKGROUND

Merchants accept consumer payments for goods and services throughpoint-of-sale (“POS”) terminals and corresponding business applications.Configuring such POS terminals and business applications to accept andprocess payment transactions is a complex and time consuming process.For example, conventional POS terminals and business applications mustbe configured to support and communicate with various different paymentnetworks as well as a variety of different card readers and PIN pads.Such configuration typically requires sophisticated programmingknowledge in connection with payment processing transactions.Additionally, POS terminals are increasingly being required to becertified by various payment networks, a process which is also complexand time consuming.

SUMMARY

In an embodiment, the present disclosure is directed, in part, to amethod for managing payment authorization request messaging for paymenttransactions, the method includes receiving, by a transaction managementcontroller and from a business management engine, a transaction amountfor a payment transaction, the transaction amount for insertion by thetransaction management controller into a payment authorization requestmessage. The method further includes requesting, by the transactionmanagement controller and from a point of interaction device, paymentcard data for the payment authorization request message, wherein thebusiness management engine is communicatively isolated from the point ofinteraction device. In addition, the method includes receiving, by thetransaction management controller and from the point of interactiondevice, the requested payment card data for insertion by the transactionmanagement controller into the payment authorization request message.The method also includes inserting, by the transaction managementcontroller, the payment card data received from the point of interactiondevice and the transaction amount received from the business managementengine into the payment authorization request message. The methodfurther includes transmitting, by the transaction management controllerand to a payment network, the payment authorization request message andreceiving, by the transaction management controller and from the paymentnetwork, a payment authorization response message for the paymentauthorization request message. The method also includes transmitting, bythe transaction management controller and to the business managementengine, the payment authorization response message for generation of areceipt.

In another embodiment, the present disclosure is directed, in part, toone or more machine-readable storage media including a plurality ofinstructions stored thereon that in response to being executed by atransaction management controller, cause the transaction managementcontroller to receive, from a business management engine, a transactionamount for a payment transaction, the transaction amount for insertionby the transaction management controller into a payment authorizationrequest message. The plurality of instructions further cause thetransaction management controller to request, from a point ofinteraction device, payment card data for the payment authorizationrequest message, wherein the business management engine iscommunicatively isolated from the point of interaction device. Theplurality of instructions also cause the transaction managementcontroller to receive, from the point of interaction device, therequested payment card data for insertion by the transaction managementcontroller into the payment authorization request message and insert thepayment card data received from the point of interaction device and thetransaction amount received from the business management engine into thepayment authorization request message. In addition, the plurality ofinstructions further cause the transaction management controller totransmit, to a payment network, the payment authorization requestmessage and receive, from the payment network, a payment authorizationresponse message for the payment authorization request message. Theplurality of instructions also cause the transaction managementcontroller to transmit, to the business management engine, the paymentauthorization response message for generation of a receipt.

In another embodiment, the present disclosure is directed, in part, to asystem for managing payment authorization request messaging for paymenttransactions, the system includes a transaction management controllercomprising a processor executing instructions stored in memory, whereinthe instructions cause the processor to receive, from a businessmanagement engine, a transaction amount for a payment transaction, thetransaction amount for insertion by the transaction managementcontroller into a payment authorization request message. Theinstructions further cause the processor to request, from a point ofinteraction device, payment card data for the payment authorizationrequest message, wherein the business management engine iscommunicatively isolated from the point of interaction device. Inaddition, the instructions cause the processor to receive, from thepoint of interaction device, the requested payment card data forinsertion by the transaction management controller into the paymentauthorization request message and insert the payment card data receivedfrom the point of interaction device and the transaction amount receivedfrom the business management engine into the payment authorizationrequest message. The instructions also cause the processor to transmit,to a payment network, the payment authorization request message andreceive, from the payment network, a payment authorization responsemessage for the payment authorization request message. In addition, theinstructions cause the processor to transmit, to the business managementengine, the payment authorization response message for generation of areceipt.

In another embodiment, the present disclosure is directed, in part, to asystem for remotely configuring transaction management controllers, thesystem includes a first transaction management controllercommunicatively coupled to a first business management engine, a firstpoint of interaction device, and a payment network, wherein the firstbusiness management controller is communicatively isolated from thefirst point of interaction device, and wherein the first transactionmanagement controller includes a first set of local features formanaging payment processing for payment transactions. In addition, thesystem includes a second transaction management controllercommunicatively coupled to a second business management engine, a secondpoint of interaction device, and the payment network, wherein the secondbusiness management engine is communicatively isolated from the secondpoint of interaction device, and wherein the second transactionmanagement controller includes a second set of local features formanaging payment processing for payment transactions. The system furtherincludes a remote configuration device having a processor executinginstructions stored in memory, wherein the instructions cause theprocessor to transmit a feature modification message to at least one ofthe first transaction management controller and the second transactionmanagement controller, the feature modification message includesconfiguration data to at least one of modify or add a feature of atleast one of the first set of local features of the first transactionmanagement controller and the second set of local features of the secondtransaction management controller.

BRIEF DESCRIPTION OF THE DRAWINGS

It is believed that certain embodiments will be better understood fromthe following description taken in conjunction with the accompanyingdrawings, in which like references indicate similar elements and inwhich:

FIG. 1 is a simplified block diagram of at least one embodiment of asystem for managing payment authorization request messaging for paymenttransactions;

FIG. 2 is a simplified block diagram of at least one embodiment of asystem for managing payment authorization request messaging formulti-lane payment transactions;

FIG. 3 is a simplified block diagram of at least one embodiment of asystem for remotely configuring transaction management controllers;

FIG. 4 is a simplified sequence flow diagram in accordance with at leastone non-limiting embodiment;

FIG. 5 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the transaction management controller ofFIG. 1 for managing payment authorization request messaging for paymenttransactions; and

FIG. 6 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the transaction management controller ofFIG. 1 for modifying payment processing features.

DETAILED DESCRIPTION

Various non-limiting embodiments of the present disclosure will now bedescribed to provide an overall understanding of the principles of thestructure, function, and use of systems and methods disclosed herein.One or more examples of these non-limiting embodiments are illustratedin the selected examples disclosed and described in detail withreference made to the figures in the accompanying drawings. Those ofordinary skill in the art will understand that systems and methodsspecifically described herein and illustrated in the accompanyingdrawings are non-limiting embodiments. The features illustrated ordescribed in connection with one non-limiting embodiment may be combinedwith the features of other non-limiting embodiments. Such modificationsand variations are intended to be included within the scope of thepresent disclosure.

The systems, apparatuses, devices, and methods disclosed herein aredescribed in detail by way of examples and with reference to thefigures. The examples discussed herein are examples only and areprovided to assist in the explanation of the apparatuses, devices,systems and methods described herein. None of the features or componentsshown in the drawings or discussed below should be taken as mandatoryfor any specific implementation of any of these the apparatuses,devices, systems or methods unless specifically designated as mandatory.In addition, elements illustrated in the figures are not necessarilydrawn to scale for simplicity and clarity of illustration. For ease ofreading and clarity, certain components, modules, or methods may bedescribed solely in connection with a specific figure. In thisdisclosure, any identification of specific techniques, arrangements,etc. are either related to a specific example presented or are merely ageneral description of such a technique, arrangement, etc.Identifications of specific details or examples are not intended to be,and should not be, construed as mandatory or limiting unlessspecifically designated as such. Any failure to specifically describe acombination or sub-combination of components should not be understood asan indication that any combination or sub-combination is not possible.It will be appreciated that modifications to disclosed and describedexamples, arrangements, configurations, components, elements,apparatuses, devices, systems, methods, etc. can be made and may bedesired for a specific application. Also, for any methods described,regardless of whether the method is described in conjunction with a flowdiagram, it should be understood that unless otherwise specified orrequired by context, any explicit or implicit ordering of stepsperformed in the execution of a method does not imply that those stepsmust be performed in the order presented but instead may be performed ina different order or in parallel.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “some example embodiments,” “one exampleembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with any embodimentis included in at least one embodiment. Thus, appearances of the phrases“in various embodiments,” “in some embodiments,” “in one embodiment,”“some example embodiments,” “one example embodiment, or “in anembodiment” in places throughout the specification are not necessarilyall referring to the same embodiment. Furthermore, the particularfeatures, structures or characteristics may be combined in any suitablemanner in one or more embodiments.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Like referencenumerals are generally intended to refer to the same or similarcomponents. Components and modules can be implemented in software,hardware, or a combination of software and hardware. The term “software”is used expansively to include not only executable code, for examplemachine-executable or machine-interpretable instructions, but also datastructures, data stores and computing instructions stored in anysuitable electronic format, including firmware, and embedded software.The terms “information” and “data” are used expansively and includes awide variety of electronic information, including executable code;content such as text, video data, and audio data, among others; andvarious codes or flags. The terms “information,” “data,” and “content”are sometimes used interchangeably when permitted by context. It shouldbe noted that although for clarity and to aid in understanding someexamples discussed herein might describe specific features or functionsas part of a specific component or module, or as occurring at a specificlayer of a computing device (for example, a hardware layer, operatingsystem layer, or application layer), those features or functions may beimplemented as part of a different component or module or operated at adifferent layer of a communication protocol stack. Those of ordinaryskill in the art will recognize that the systems, apparatuses, devices,and methods described herein can be applied to, or easily modified foruse with, other types of equipment, can use other arrangements ofcomputing systems such as client-server distributed systems, and can useother protocols, or operate at other layers in communication protocolstacks, than are described.

For simplicity, the description that follows will be provided byreference to a “payment vehicle” or a “payment card,” which generallyrefers to any type of financial alternative to currency. As is to beclear to those skilled in the art, no aspect of the present disclosureis specifically limited to a specific type of payment vehicle or paymentcard. Therefore, it is intended that the following descriptionencompasses the use of the present disclosure with many other forms offinancial alternatives to currency, including credit cards, debit cards,smart cards, single-use cards, pre-paid cards, electronic currency (suchas might be provided through a cellular telephone or personal digitalassistant), and the like. Payment vehicles or payment card can betraditional plastic transaction cards, titanium-containing, or othermetal-containing, transaction cards, clear and/or translucenttransaction cards, foldable or otherwise unconventionally-sizedtransaction cards, radio-frequency enabled transaction cards, or othertypes of transaction cards, such as credit, charge, debit, pre-paid orstored-value cards, or any other like financial transaction instrument.

Referring now to FIG. 1, in one embodiment, a system 100 for managingpayment authorization request messaging for payment transactionsincludes a transaction management controller 102, a business managementengine 120, a point of interaction (POI) device 130, and a paymentnetwork 140. In some embodiments, the system 100 includes a remoteconfiguration device 150. In operation, the transaction managementcontroller 102 receives a payment request from the business managementengine 120 in connection with a payment transaction. The payment requestincludes a transaction amount and can be embodied as a HypertextTransfer Protocol (HTTP) message. After receiving the payment request,the transaction management controller 102 requests payment card data(e.g., a payment card number, a payment card type, etc.) for the paymenttransaction from the POI device 130 (e.g., a card reader, a PIN pad,etc.). In the illustrative embodiment, the POI device 130 iscommunicatively isolated from the business management engine 120.

Once the payment card data is received from the POI device 130, thetransaction management controller 102 inserts the received transactionamount and the payment card data into a payment authorization requestmessage. The transaction management controller 102 transmits the paymentauthorization request message to the payment network 140, which asdescribed in more detail below, can be embodied as, or otherwiseinclude, a payment gateway (not shown). A payment authorization responsemessage is then received from the payment network 140 (or the paymentgateway) in response to the payment authorization request message. Thetransaction management controller 102 transmits the received paymentauthorization response message to the business management engine 120.

In some embodiments, the transaction management controller 102 isconfigured to interface with and control features and/or functionalityof the POI device 130. For example, in some embodiments, the transactionmanagement controller 102 can be configured to control selectableoptions (e.g., payment card type selections, cashback selections,transaction amount verification, language selections, etc.) that are tobe displayed to a consumer via the POI device 130. Additionally oralternatively, the transaction management controller 102 can beconfigured to control payment transaction processing features (e.g.,signature prompting features, PIN entry features, customizedinformational display screens, scrolling receipt features, etc.)provided by the POI device 130.

The transaction management controller 102 can be embodied as any type ofcomputing device or server or capable of processing, communicating,storing, maintaining, and transferring data. For example, thetransaction management controller 102 can be embodied as a server, amicrocomputer, a minicomputer, a mainframe, a desktop computer, a laptopcomputer, a mobile computing device, a handheld computer, a smart phone,a tablet computer, a personal digital assistant, a telephony device, acustom chip, an embedded processing device, or other computing deviceand/or suitable programmable device. In some embodiments, thetransaction management controller 102 can be embodied as a computingdevice integrated with other systems or subsystems. In the illustrativeembodiment of FIG. 1, the transaction management controller 102 includesa processor 104, a system bus 106, a memory 108, a data storage 110,communication circuitry 112, and one or more peripheral devices 114. Ofcourse, the transaction management controller 102 can include other oradditional components, such as those commonly found in a server and/orcomputer (e.g., various input/output devices), in other embodiments.Additionally, in some embodiments, one or more of the illustrativecomponents can be incorporated in, or otherwise from a portion of,another component. For example, the memory 108, or portions thereof, canbe incorporated in the processor 104 in some embodiments. Furthermore,it should be appreciated that the transaction management controller 102can include other components, sub-components, and devices commonly foundin a computer and/or computing device, which are not illustrated in FIG.1 for clarity of the description.

The processor 104 can be embodied as any type of processor capable ofperforming the functions described herein. For example, the processor104 can be embodied as a single or multi-core processor, a digitalsignal processor, microcontroller, a general purpose central processingunit (CPU), a reduced instruction set computer (RISC) processor, aprocessor having a pipeline, a complex instruction set computer (CISC)processor, an application specific integrated circuit (ASIC), aprogrammable logic device (PLD), a field programmable gate array (FPGA),or other processor or processing/controlling circuit or controller.

In various configurations, the transaction management controller 102includes a system bus 106 for interconnecting the various components ofthe transaction management controller 102. The system bus 106 can beembodied as, or otherwise include, memory controller hubs, input/outputcontrol hubs, firmware devices, communication links (i.e.,point-to-point links, bus links, wires, cables, light guides, printedcircuit board traces, etc.) and/or other components and subsystems tofacilitate the input/output operations with the processor 104, thememory 108, and other components of the transaction managementcontroller 102. In some embodiments, the transaction managementcontroller 102 can be integrated into one or more chips such as aprogrammable logic device or an application specific integrated circuit(ASIC). In such embodiments, the system bus 106 can form a portion of asystem-on-a-chip (SoC) and be incorporated, along with the processor104, the memory 108, and other components of the transaction managementcontroller 102, on a single integrated circuit chip.

The memory 108 can be embodied as any type of volatile or non-volatilememory or data storage capable of performing the functions describedherein. For example, the memory 108 can be embodied as read only memory(ROM), random access memory (RAM), cache memory associated with theprocessor 104, or other memories such as dynamic RAM (DRAM), static ram(SRAM), programmable ROM (PROM), electrically erasable PROM (EEPROM),flash memory, a removable memory card or disk, a solid state drive, andso forth. In operation, the memory 108 can store various data andsoftware used during operation of the transaction management controller102 such as operating systems, applications, programs, libraries, anddrivers.

The data storage 110 can be embodied as any type of device or devicesconfigured for short-term or long-term storage of data such as, forexample, memory devices and circuits, memory cards, hard disk drives,solid-state drives, or other data storage devices. For example, in someembodiments, the data storage 110 includes storage media such as astorage device that can be configured to have multiple modules, such asmagnetic disk drives, floppy drives, tape drives, hard drives, opticaldrives and media, magneto-optical drives and media, compact disc drives,Compact Disc Read Only Memory (CD-ROM), Compact Disc Recordable (CD-R),Compact Disc Rewriteable (CD-RW), a suitable type of Digital VersatileDisc (DVD) or Blu-Ray disc, and so forth. Storage media such as flashdrives, solid state hard drives, redundant array of individual disks(RAID), virtual drives, networked drives and other memory meansincluding storage media on the processor 104, or the memory 108 are alsocontemplated as storage devices. It should be appreciated that suchmemory can be internal or external with respect to operation of thedisclosed embodiments. It should also be appreciated that certainportions of the processes described herein can be performed usinginstructions stored on a computer-readable medium or media that director otherwise instruct a computer system to perform the process steps.Non-transitory computer-readable media, as used herein, comprises allcomputer-readable media except for transitory, propagating signals.

In some embodiments, the data storage device 110 can be configured tostore a set of local payment processing features of the transactionmanagement controller 102. Each feature can be configured to providedifferent functionality of the transaction management controller 102and/or the POI device 130. As such, each feature can be toggled “on” ortoggled “off” to control the features provided by the transactionmanagement controller 102 and/or the POI device 130. The local paymentprocessing features can include device configuration features and/orsettings (e.g., listening port settings, security settings, usersettings, etc.), transaction professing features and/or settings (e.g.,partial approval features, transaction amount confirmation features,cashback features, accepted payment card settings, supported languagesettings, transaction gratuity features, signature requirement features,transaction store and forward features, etc.), multilane features and/orsettings (e.g., lane identification features, lane initializationsettings, etc.), POI device 130 features and/or settings (e.g., terminaltype settings, driver configurations, communication settings, etc.), andany other type of payment processing feature or configuration settingfor the transaction management controller 102 or a device controlled ormanaged thereby (e.g., the POI device 130).

The communication circuitry 112 of the transaction management controller102 may be embodied as any type of communication circuit, device,interface, or collection thereof, capable of enabling communicationsbetween the transaction management controller 102 and the businessmanagement engine 120, POI device 130, payment network 140, remoteconfiguration device 150, and/or any other computing devicecommunicatively coupled thereto. For example, the communicationcircuitry 112 may be embodied as one or more network interfacecontrollers (NICs), in some embodiments. The communication circuitry 112may be configured to use any one or more communication technologies(e.g., wireless or wired communications) and associated protocols (e.g.,Ethernet, Wi-Fi®, WiMAX, etc.) to effect such communication.

In some embodiments, the transaction management controller 102, businessmanagement engine 120, POI device 130, payment network 140, remoteconfiguration device 150, and/or any other computing devices of thesystem 100, can communicate with each other over one or more networks.The network(s) can be embodied as any number of various wired and/orwireless communication networks. For example, the network(s) can beembodied as or otherwise include a local area network (LAN), a wide areanetwork (WAN), a cellular network, or a publicly-accessible, globalnetwork such as the Internet. Additionally, the network(s) can includeany number of additional devices to facilitate communication between thecomputing devices of the system 100.

Additionally, in some embodiments, the transaction management controller102 can further include one or more peripheral devices 114. Suchperipheral devices 114 can include any type of peripheral devicecommonly found in a computing device such as additional data storage,speakers, a hardware keyboard, a keypad, a gesture or graphical inputdevice, a motion input device, a touchscreen interface, one or moredisplays, an audio unit, a voice recognition unit, a vibratory device, acomputer mouse, a peripheral communication device, and any othersuitable user interface, input/output device, and/or other peripheraldevice.

The business management engine 120 can be embodied as any type ofcomputing device capable of performing the functions described herein.As such, the business management engine 120 can include devices andstructures commonly found in computing devices such as processors,memory devices, communication circuitry, and data storages, which arenot shown in FIG. 1 for clarity of the description. The businessmanagement engine 120 can be configured to perform certainbusiness-related functions, such as, without limitation, inventorymanagement, scheduling, accounting processes, payroll, and the like. Asis to be appreciated, the particular business-related functionsfacilitated by a business management engine may depend on the needs ofthe particular business (e.g., merchant) utilizing the businessmanagement engine. In this regard, a business management engine of asalon may provide different business-related functions than that of aspecialty retailer, for example. In some embodiments, the businessmanagement engine 120 is configured to initiate payment transactions. Asdiscussed in more detail below, the business management engine 120 isconfigured to communicate with the transaction management controller 102to facilitate such payment transactions. For example, in someembodiments, the business management engine 120 is configured totransmit a payment request to the transaction management controller 102.The payment request can be embodied as an HTTP message that includes theamount of the transaction. Additionally, the business management engine120 can be configured to receive a payment authorization responsemessage from the transaction management controller 102. As discussed inmore detail below, the business management engine 120 can becommunicatively isolated from the POI device 130 (e.g., not in directcommunication with the POI device 130). As such, instead of beingdirectly connected to the POI device 130, the business management engine120 is communicatively coupled to the transaction management controller102, which manages communications with the POI device 130. It should beappreciated that in doing so, the complexity of configuring (e.g.,coding, certification, initialization, etc.) of the business managementengine 120 is reduced.

Additionally, in some embodiments, the business management engine 120can transmit data to the transaction management controller 102 forsubsequent display on the POI device 130 during a purchase or paymenttransaction. For example, in some embodiments, the business managementengine 120 can be configured to transmit scrolling receipt data to thetransaction management device 102. In turn, the transaction managementdevice 102 can transmit the scrolling receipt data to the POI device130. In such embodiments, the scrolling receipt data can include productscan data (e.g., product identifiers, product names, productdescriptions, etc.) and product sales price data. It should beappreciated that the scrolling receipt data can include any other typeof data associated with a purchase or payment transaction.

The point of interaction (POI) device 130 can be embodied as any type ofcomputing or payment device capable of performing the functionsdescribed herein. For example, in the illustrative embodiment, the POIdevice 130 can be embodied as a card reader or a PIN pad configured tofacilitate receipt of a payment card for a payment transaction (e.g., acredit or debit transaction). The POI device 130 can include devices andstructures commonly found in computing and payment devices such asprocessors, memory devices, communication circuitry, and data storages,which are not shown in FIG. 1 for clarity of the description. Asdiscussed, in some embodiments, the POI device 130 is communicativelyisolated from the business management engine 120. In such embodiments,the POI device 130 instead communicates directly with the transactionmanagement controller 102 via a wired or wireless communication link(i.e., a point-to-point link, bus link, wire, cable, light guide,printed circuit board traces, wireless link, etc.). As such, the POIdevice 130 can be controlled by the transaction management controller102, which can include the necessary drivers to do so.

The payment network 140 can be, for example, a network of a credit cardassociation affiliated with a payment vehicle or payment card (e.g.,credit cards, debit cards, smart cards, single-use cards, pre-paidcards, electronic currency, etc.), which generally refers to any type offinancial alternative to currency. Non-limiting examples of credit cardassociations include VISA, MASTERCARD, DISCOVER, and AMERICAN EXPRESS.In some embodiments, the payment network 140 receives a paymentauthorization request message from the transaction management controller102 for a payment transaction. The payment network 140 can provide thepayment authorization request message to a payment processing server ofan issuer processor, which in turn can provide the payment authorizationrequest message to an issuer financial institution. The issuer financialinstitution can then associate the payment vehicle or payment card usedwith an account held by the issuer financial institution. Thereafter,the issuer financial institution can transmit a payment authorizationresponse message to the payment network 140 via the issuer processor. Inresponse to receiving the payment authorization response message, thepayment network 140 can transmit the payment authorization responsemessage to the transaction management controller 102. In someembodiments, the payment network 140 includes a payment gateway (notshown) configured to facilitate the transaction management controller102 or, more generally, merchants in processing payment transactions.

The remote configuration device 150 can be embodied as any type ofcomputing device capable of performing the functions described herein.As such, the remote configuration device 150 can include devices andstructures commonly found in computing devices such as processors,memory devices, communication circuitry, and data storages, which arenot shown in FIG. 1 for clarity of the description. In some embodiments,the remote configuration device 150 is configured to configure and/ormanage payment processing features of the transaction managementcontroller 102, multiple transaction management controllers (e.g., thetransaction management controller 312 and the transaction managementcontroller 322 illustratively shown in FIG. 3), and/or other devices ofthe system 100 (e.g., the POI device 130). To do so, the remoteconfiguration device 150 can generate one or more feature modificationmessage, which can be transmitted to the transaction managementcontroller. As discussed in more detail below, the feature modificationmessage can include configuration data, which can be used by thetransaction management controller 102 to add or modify a local paymentprocessing feature. In embodiments in which the remote configurationdevice 150 is configured to configure and/or manage multiple transactionmanagement controllers, the remote configuration device 150 canselectively transmit feature modification messages to each transactionmanagement controller.

In some embodiments, the transaction management controller 102, thebusiness management engine 120, the point of interaction device 130, thepayment network 140 (or computing devices thereof), and the remoteconfiguration device 150 can each establish an environment duringoperation. Each environment can include various modules, components,sub-components, and devices commonly found in computing devices, whichare not illustrated in the figures for clarity of the description. Thevarious modules, components, sub-components, and devices of eachenvironment can be embodied as hardware, firmware, software, or acombination thereof. For example, one or more of the modules,components, sub-components, and devices of each environment can beembodied as a processor and/or a controller configured to provide thefunctionality described herein.

Referring now to FIG. 2, in an embodiment, a system 200 for managingpayment authorization request messaging for multi-lane paymenttransactions includes the transaction management controller 102, thebusiness management engine 120, multiple point of interaction (POI)devices 130 (e.g., the POI device 130 a, POI device 130 b, POI device130 n, etc.), and the payment network 140. In some embodiments, thesystem 200 includes the remote configuration device 150. Asillustratively shown, the transaction management controller 102 canmanage and, therefore, be communicatively coupled to multiple POIdevices 130. Each POI device 130 (e.g., the POI device 130 a, POI device130 b, POI device 130 n, etc.) of the system 200 may be embodied as adifferent “lane” in a multi-lane environment. As such, it should beappreciated that each of the devices illustratively shown in FIG. 2 maybe substantially similar to the devices illustratively shown anddescribed with respect to FIG. 1.

Referring now to FIG. 3, in an embodiment, a system 300 for configuringmultiple transaction management controllers includes the remoteconfiguration device 150 and the payment network 140. The system 300also includes a transaction management controller 312, a businessmanagement engine 314, and a POI device 316 of one merchant environment(e.g., the merchant environment A 310) and a transaction managementcontroller 322, a business management engine 324, and a POI device 326of another merchant environment (e.g., the merchant environment B 320).It should be appreciated that the transaction management controllers312, 322, business management engines 314, 324, POI devices 316, 326,payment network 140, and remote configuration device 150 of the system300 can be substantially similar to the transaction managementcontroller 102, business management engine 120, POI device 130, paymentnetwork 140, and remote configuration device 150 of the system 100 ofFIG. 1. In the illustrative embodiment, however, the remoteconfiguration device 150 is configured to selectively manage multipletransaction management controllers (e.g., the transaction managementcontrollers 312, 322).

Referring now to FIG. 4, a process 400 that may be executed by thedevices of the system 100 begins with process flow 402. In process flow402, the business management engine 120 transmits a payment request tothe transaction management controller 102. The payment request includesa transaction amount and can be embodied as a Hypertext TransferProtocol (HTTP) message. In embodiments in which the payment request isan HTTP message, the payment request can be embodied as an HTTP POSTrequest or an HTTP PUT request. In such embodiments, one or more paymentrequest parameters (e.g., transaction amount, payment type, etc.) can besent to the transaction management controller 102 within a uniformresource locator (URL) that corresponds to the transaction managementcontroller 102. Additionally or alternatively, the payment request canbe embodied as an HTTP GET request or an HTTP DELETE request. In suchembodiments, one or more of the payment request parameters can be sentto the transaction management controller 102 within the body of the HTTPmessage sent to the transaction management controller 102. Next, inprocess flow 404, the transaction management controller 102 initiationsa payment transaction based at least in part on, or otherwise as afunction of, the received payment request.

Subsequently, in process flow 406, the transaction management controller102 requests payment card data for the initiated payment transactionfrom the POI device 130. In some embodiments, in processes flow 406, thetransaction management controller 102 additionally manages paymentselection options provided to a consumer via the POI device 130. Forexample, the transaction management controller 102 can transmit one ormore instructions to the POI device 130 that cause the POI device 130 todisplay one or more selectable options (e.g., payment card typeselection options, cashback selection options, language selectionoptions, etc.) to a consumer. Additionally, as discussed above, thetransaction management controller 102 can control other features and/orfunctions of the POI device 130 corresponding to a payment transaction.

In process flow 408, the POI device 130 transmits the payment card datato the transaction management controller 102. The payment card data canbe captured by the POI device 130 in response to receipt of the requestfrom the transaction management controller 102. Additionally, inembodiments in which the transaction management controller 102 managesthe payment selection options provided to the consumer during thepayment transaction, the selected options can be transmitted by the POI130 to the transaction management controller 102.

Subsequently, in process flow 410, the transaction management controller102 transmits transaction data for the payment transaction to thepayment network 140 for processing. To do so, the transaction managementcontroller inserts or incorporates the transaction amount received fromthe business management engine 120 and the payment card data receivedfrom the POI device 130 into a payment authorization request message. Insome embodiments, the payment authorization request message can beembodied as a HTTP message. Additionally, in some embodiments, thepayment network 140 includes a payment gateway. In such embodiments, thepayment gateway is configured to receive the payment authorizationrequest message from the transaction management controller 102.

In process flow 412, the payment network 140 processes the paymenttransaction based on the payment authorization response message receivedfrom the transaction management controller 102. As discussed, thepayment network 140 is configured to receive and forward the paymentauthorization request message to an issuer financial institution via anissuer processor. Thereafter, the issuer financial institutionassociates the received payment card number with an account held and/ormaintained by the issuer financial institution. After associating thereceived payment card number with an account, the issuer financialinstitution generates a payment authorization response message. Thepayment authorization response message can then be transmitted to thepayment network 140 via the issuer processor. Next, in process flow 414,the payment network 140 (or the payment gateway of the payment network140) transmits the received payment authorization response message tothe transaction management controller 102.

Subsequently, in process flow 416, the transaction management controller102 and the POI device 130 finalize the payment transaction and, in someembodiments, the payment authorization response message. For example, insome embodiment, the transaction management controller 102 can instructthe POI device 130 to capture a signature for the payment transaction.Additionally or alternatively, in some embodiments, an integratedcircuit payment card (e.g., an EMV card or other smartcard) can beinserted into the POI device 130, which can include correspondingintegrated circuit hardware and functionality. In such embodiments, thetransaction management controller 102 can instruct the POI device 130 towrite payment transaction data or account data back to the integratedcircuit payment card. It should be appreciated that the transactionmanagement controller 102 and the POI device 130 can perform any otherfunction to finalize the payment transaction.

In process flow 418, the transaction management controller 102 transmitsthe finalized payment authorization response message to the businessmanagement engine 120. In some embodiments, the business managementengine 120 generates a receipt for the payment transaction based atleast in part on, or otherwise as a function of, the finalized paymentauthorization response message received from the transaction managementcontroller 102.

Referring now to FIG. 5, a method 500 that may be executed by thetransaction management controller 102 for managing payment authorizationrequest messaging for payment transactions begins with decision block502. In decision block 502, the transaction management controller 102determines whether a payment request for a payment transaction isreceived from the business management engine 120. The payment requestcan include a transaction amount and can be embodied as a HypertextTransfer Protocol (HTTP) message. If, in decision block 502, thetransaction management controller 102 determines that a payment requestis received, the method 500 advances to block 504. If, however, thetransaction management controller 102 determines instead that a paymentrequest is not received, the method 500 loops back to decision block 502and the transaction management controller 102 continues monitoring forreceipt of a payment request.

In block 504, the transaction management controller 102 requests paymentcard data for the payment transaction from the POI device 130. In someembodiments, in block 506, the transaction management controller managesselection options of the POI device 130 for the payment transaction. Forexample, the transaction management controller 102 can transmit one ormore instructions to the POI device 130 that cause the POI device 130 todisplay payment card type selection options, cashback selection options,language selection options, or any other type of option selectable by aconsumer during a payment transaction.

In block 508, the transaction management controller 102 receives therequested payment card data from the POI device 130. In someembodiments, the received payment card data includes a payment cardnumber associated with a payment card used for the payment transaction.It should be appreciated, however, that the payment card data caninclude any other type of data associated with a payment transaction. Insome embodiments, in block 510, the transaction management controller102 receives any payment options selected by a consumer via the POIdevice 130.

In block 512, the transaction management controller 102 inserts orotherwise incorporates the transaction amount received from the businessmanagement engine 120 and the payment card data (e.g., the payment cardnumber, etc.) received from the POI device 130 into a paymentauthorization request message. In some embodiments, the paymentauthorization request message can be embodied as a HTTP message. Itshould be appreciated, however, that the payment authorization requestmessage can be embodied as any other type of message, in otherembodiments.

In block 514, the transaction management controller 102 transmits thepayment authorization request message to the payment network 140. Asdiscussed, the payment network 140 can include a payment gatewaycommunicatively coupled thereto configured to facilitate the transactionmanagement controller 102 in processing payment transactions, in someembodiments. The payment network 140 can be configured to communicatewith an issuer processor and/or and issuer financial institution and,based on the payment authorization request message, generate a paymentauthorization response message. In block 516, the transaction managementcontroller 102 receives the payment authorization response message fromthe payment network 140 (or a payment gateway communicatively coupledthereto). In some embodiments, the payment authorization responsemessage can be embodied as a HTTP message. It should be appreciated,however, that the payment authorization response message can be embodiedas any other type of message, in other embodiments.

Subsequently, in block 518, the transaction management controller 102finalizes the payment transaction and, in some embodiments, the paymentauthorization response message with the POI device 130. For example, insome embodiments, the transaction management controller 102 can instructthe POI device 130 to capture a signature for the payment transaction.In such embodiments, the transaction management controller 102 canreceive captured signature data from the POI device 130. Additionally,in such embodiments, the payment authorization response message can bemodified or augmented to include a byte array of the captured signaturedata. Additionally or alternatively, in some embodiments, thetransaction management controller 102 can instruct the POI device 130 towrite payment transaction data or account data back to an integratedcircuit payment card used for a particular payment transaction.

In block 520, the transaction management controller 102 transmits thefinalized payment authorization response message to the businessmanagement engine 120. In some embodiments, the business managementengine 120 generates a receipt for the payment transaction based atleast in part on, or otherwise as a function of, the finalized paymentauthorization response message received from the transaction managementcontroller 102. In such embodiments, the business management engine 120can be configured to print the generated receipt via a receipt printercommunicatively coupled thereto.

Referring now to FIG. 6, a method 600 that may be executed by thetransaction management controller 102 for modifying payment processingfeatures begins with block 602. In block 602, the transaction managementcontroller 102 receives a feature modification message from the remoteconfiguration device 150. The feature modification message includesconfiguration data or instructions to at least one of add or modify alocal payment processing feature of the transaction managementcontroller 102 and/or other devices of the system 100 (e.g., the POIdevice 130).

In block 604, the transaction management controller 102 modifies one ormore local payment processing features based at least in part on, orotherwise as a function of, the received feature modification message.For example, in some embodiments, the transaction management controller102 can, in block 606, toggle “on” or “off” (e.g., enable or disable)one or more local features based on the configuration data of thereceived feature modification message. In that way, the transactionmanagement controller 102 (or other devices of the systems 100, 200,300) can be remotely managed and configured.

Some of the figures can include a flow diagram. Although such figurescan include a particular logic flow, it can be appreciated that thelogic flow merely provides an exemplary implementation of the generalfunctionality. Further, the logic flow does not necessarily have to beexecuted in the order presented unless otherwise indicated. In addition,the logic flow can be implemented by a hardware element, a softwareelement executed by a computer, a firmware element embedded in hardware,or any combination thereof.

The foregoing description of embodiments and examples has been presentedfor purposes of illustration and description. It is not intended to beexhaustive or limiting to the forms described. Numerous modificationsare possible in light of the above teachings. Some of thosemodifications have been discussed, and others will be understood bythose skilled in the art. The embodiments were chosen and described inorder to best illustrate principles of various embodiments as are suitedto particular uses contemplated. The scope is, of course, not limited tothe examples set forth herein, but can be employed in any number ofapplications and equivalent devices by those of ordinary skill in theart. Rather it is hereby intended the scope of the invention to bedefined by the claims appended hereto.

1. A method for managing payment authorization request messaging forpayment transactions, the method comprising: receiving, by a transactionmanagement controller and from a business management engine, atransaction amount for a payment transaction, the transaction amount forinsertion by the transaction management controller into a paymentauthorization request message; requesting, by the transaction managementcontroller and from a point of interaction device, payment card data forthe payment authorization request message, wherein the businessmanagement engine is communicatively isolated from the point ofinteraction device; receiving, by the transaction management controllerand from the point of interaction device, the requested payment carddata for insertion by the transaction management controller into thepayment authorization request message; inserting, by the transactionmanagement controller, the payment card data received from the point ofinteraction device and the transaction amount received from the businessmanagement engine into the payment authorization request message;transmitting, by the transaction management controller and to a paymentnetwork, the payment authorization request message; receiving, by thetransaction management controller and from the payment network, apayment authorization response message for the payment authorizationrequest message; and transmitting, by the transaction managementcontroller and to the business management engine, the paymentauthorization response message for generation of a receipt.
 2. Themethod of claim 1, further comprising: managing, by the transactionmanagement controller, selection options of the point of interactiondevice for the payment transaction; and receiving, by the transactionmanagement controller and from the point of interaction device, selectedoptions for the payment transaction.
 3. The method of claim 1, whereinthe authorization request message and the authorization response messagecomprise Hypertext Transfer Protocol messages.
 4. The method of claim 1,further comprising: receiving, by the transaction management controllerand from the business management engine, product scan data andcorresponding price data for a purchase transaction; and managing, bythe transaction management controller, display of the product scan dataand corresponding price data on the point of interaction device.
 5. Themethod of claim 1, further comprising receiving, by the transactionmanagement controller, a feature modification message from a remoteconfiguration device, the feature modification message comprisesconfiguration data to at least one of modify or add a feature of thetransaction management controller.
 6. The method of claim 5, wherein toat least one of modify or add the feature of the transaction managementcontroller comprises to toggle on or toggle off the feature of thetransaction management controller based at least in part on theconfiguration data of the feature modification message.
 7. The method ofclaim 5, wherein the feature of the transaction management controllercomprises at least one of an accepted payment type feature, atransaction store and forward feature, a signature prompt feature forthe point of interaction device, a customized display screen for thepoint of interaction device, and a scrolling receipt feature for thepoint of interaction device.
 8. The method of claim 1, furthercomprising receiving, by the transaction management controller and fromthe point of interaction device, captured signature data; and whereinthe payment authorization response message transmitted to the businessmanagement engine comprises a byte array of the captured signature data.9. The method of claim 1, wherein transmitting the payment authorizationrequest message to a payment network comprises transmitting the paymentauthorization request message to a payment gateway communicativelycoupled to the payment network; and wherein receiving the paymentauthorization response message from the payment network comprisesreceiving the payment authorization response message from the paymentgateway communicatively coupled to the payment network.
 10. One or moremachine-readable storage media comprising a plurality of instructionsstored thereon that in response to being executed by a transactionmanagement controller, cause the transaction management controller to:receive, from a business management engine, a transaction amount for apayment transaction, the transaction amount for insertion by thetransaction management controller into a payment authorization requestmessage; request, from a point of interaction device, payment card datafor the payment authorization request message, wherein the businessmanagement engine is communicatively isolated from the point ofinteraction device; receive, from the point of interaction device, therequested payment card data for insertion by the transaction managementcontroller into the payment authorization request message; insert thepayment card data received from the point of interaction device and thetransaction amount received from the business management engine into thepayment authorization request message; transmit, to a payment network,the payment authorization request message; receive, from the paymentnetwork, a payment authorization response message for the paymentauthorization request message; and transmit, to the business managementengine, the payment authorization response message for generation of areceipt.
 11. The one or more machine-readable storage media of claim 10,wherein the plurality of instructions further cause the transactionmanagement controller to: manage selection options of the point ofinteraction device for the payment transaction; and receive, from thepoint of interaction device, selected options for the paymenttransaction.
 12. The one or more machine-readable storage media of claim10, wherein the authorization request message and the authorizationresponse message comprise Hypertext Transfer Protocol messages.
 13. Theone or more machine-readable storage media of claim 10, wherein theplurality of instructions further cause the transaction managementcontroller to: receive, from the business management engine, productscan data and corresponding price data for a purchase transaction; andmanage display of the product scan data and corresponding price data onthe point of interaction device.
 14. The one or more machine-readablestorage media of claim 10, wherein the plurality of instructions furthercause the transaction management controller to receive a featuremodification message from a remote configuration device, the featuremodification message comprises configuration data to at least one ofmodify or add a feature of the transaction management controller. 15.The one or more machine-readable storage media of claim 14, wherein toat least one of modify or add the feature of the transaction managementcontroller comprises to toggle on or toggle off the feature of thetransaction management controller based at least in part on theconfiguration data of the feature modification message.
 16. The one ormore machine-readable storage media of claim 14, wherein the feature ofthe transaction management controller comprises at least one of anaccepted payment type feature, a transaction store and forward feature,a signature prompt feature for the point of interaction device, acustomized display screen for the point of interaction device, and ascrolling receipt feature for the point of interaction device.
 17. Theone or more machine-readable storage media of claim 10, wherein theplurality of instructions further cause the transaction managementcontroller to receive captured signature data from the point ofinteraction device; and wherein the payment authorization responsemessage transmitted to the business management engine comprises a bytearray of the captured signature data.
 18. The one or moremachine-readable storage media of claim 10, wherein to transmit thepayment authorization request message to a payment network comprises totransmit the payment authorization request message to a payment gatewaycommunicatively coupled to the payment network; and wherein to receivethe payment authorization response message from the payment networkcomprises to receive the payment authorization response message from thepayment gateway communicatively coupled to the payment network.
 19. Asystem for managing payment authorization request messaging for paymenttransactions, the system comprising: a transaction management controllercomprising a processor executing instructions stored in memory, whereinthe instructions cause the processor to: receive, from a businessmanagement engine, a transaction amount for a payment transaction, thetransaction amount for insertion by the transaction managementcontroller into a payment authorization request message; request, from apoint of interaction device, payment card data for the paymentauthorization request message, wherein the business management engine iscommunicatively isolated from the point of interaction device; receive,from the point of interaction device, the requested payment card datafor insertion by the transaction management controller into the paymentauthorization request message; insert the payment card data receivedfrom the point of interaction device and the transaction amount receivedfrom the business management engine into the payment authorizationrequest message; transmit, to a payment network, the paymentauthorization request message; receive, from the payment network, apayment authorization response message for the payment authorizationrequest message; and transmit, to the business management engine, thepayment authorization response message for generation of a receipt. 20.The system of claim 19, wherein the instructions of the transactionmanagement controller further cause the processor to: manage selectionoptions of the point of interaction device for the payment transaction;and receive, from the point of interaction device, selected options forthe payment transaction.
 21. The system of claim 19, wherein theauthorization request message and the authorization response messagecomprise Hypertext Transfer Protocol messages.
 22. The system of claim19, wherein the instructions of the transaction management controllerfurther cause the processor to: receive, from the business managementengine, product scan data and corresponding price data for a purchasetransaction; and manage display of the product scan data andcorresponding price data on the point of interaction device.
 23. Thesystem of claim 19, wherein the instructions of the transactionmanagement controller further cause the processor to receive a featuremodification message from a remote configuration device, the featuremodification message comprises configuration data to at least one ofmodify or add a feature of the transaction management controller. 24.The system of claim 23, wherein to at least one of modify or add thefeature of the transaction management controller comprises to toggle onor toggle off the feature of the transaction management controller basedat least in part on the configuration data of the feature modificationmessage.
 25. The system of claim 23, wherein the feature of thetransaction management controller comprises at least one of an acceptedpayment type feature, a transaction store and forward feature, asignature prompt feature for the point of interaction device, acustomized display screen for the point of interaction device, and ascrolling receipt feature for the point of interaction device.
 26. Thesystem of claim 19, wherein the instructions of the transactionmanagement controller further cause the processor to receive capturedsignature data from the point of interaction device; and wherein thepayment authorization response message transmitted to the businessmanagement engine comprises a byte array of the captured signature data.27. The system of claim 19, wherein to transmit the paymentauthorization request message to a payment network comprises to transmitthe payment authorization request message to a payment gatewaycommunicatively coupled to the payment network; and wherein to receivethe payment authorization response message from the payment networkcomprises to receive the payment authorization response message from thepayment gateway communicatively coupled to the payment network.
 28. Asystem for remotely configuring transaction management controllers, thesystem comprising: a first transaction management controllercommunicatively coupled to a first business management engine, a firstpoint of interaction device, and a payment network, wherein the firstbusiness management controller is communicatively isolated from thefirst point of interaction device, and wherein the first transactionmanagement controller comprises a first set of local features formanaging payment processing for payment transactions; a secondtransaction management controller communicatively coupled to a secondbusiness management engine, a second point of interaction device, andthe payment network, wherein the second business management engine iscommunicatively isolated from the second point of interaction device,and wherein the second transaction management controller comprises asecond set of local features for managing payment processing for paymenttransactions; and a remote configuration device comprising a processorexecuting instructions stored in memory, wherein the instructions causethe processor to transmit a feature modification message to at least oneof the first transaction management controller and the secondtransaction management controller, the feature modification messagecomprises configuration data to at least one of modify or add a featureof at least one of the first set of local features of the firsttransaction management controller and the second set of local featuresof the second transaction management controller.
 29. The system of claim28, wherein to at least one of modify or add the feature of at least oneof the first set of local features of the first transaction managementcontroller and the second set of local features of the secondtransaction management controller comprises to toggle on or toggle offthe feature of at least one of the first set of local features of thefirst transaction management controller and the second set of localfeatures of the second transaction management controller based at leastin part on the configuration data of the feature modification message.30. The system of claim 28, wherein the feature of at least one of thefirst transaction management controller and the second transactionmanagement controller comprises at least one of an accepted payment typefeature, a transaction store and forward feature, a signature promptfeature for a respective point of interaction device, a customizeddisplay screen for the respective point of interaction device, and ascrolling receipt feature for the respective point of interactiondevice.